npx workos migrations export-template saml_connections --output saml_connections.csv
npx workos migrations export-template oidc_connections --output oidc_connections.csv

Add these commands to the workos-migrations CLI.

SAML columns: organizationName organizationId organizationExternalId domains idpEntityId idpUrl x509Cert idpMetadataUrl customEntityId customAcsUrl idpIdAttribute emailAttribute firstNameAttribute lastNameAttribute idpInitiatedEnabled requestSigningKey assertionEncryptionKey nameIdEncryptionKey importedId
fooCorp foo-corp-123 foorcorp.com https://example.okta.com/app/saml/... foorCorp123 https://api.foocorp.com/saml/acs/customer TRUE

OIDC columns: organizationName organizationId organizationExternalId domains clientId clientSecret discoveryEndpoint customRedirectUri importedId
fooCorp foo-corp-123 foorcorp.com

What T-Rex did

• Before artifact, base installed @workos/migrations 2.0.0 and export-template was not exposed in top-level commands/help.
• After artifact, upgraded @workos/migrations to 2.4.0 and introduced export-template surface with options and split templates named saml_connections and oidc_connections.
• After artifact, export --help, export saml --help, export oidc --help, and export authkit --help fall back to top-level help rather than a unified export/provider surface, and nameAttribute is absent from captured help.

_{Ran code and verified through T-Rex}

1. package.json, line 89-91 (link)

   Align Node engine
   @workos/migrations@2.4.0 now resolves commander@15.0.0, whose lockfile entry requires node >=22.12.0 (pnpm-lock.yaml lines 1636-1638). This package still advertises >=22.11, so users on Node 22.11.x satisfy the CLI engine but install a dependency tree with an unmet engine requirement; with engine-strict, installs reject for a supported runtime. Please raise the root engine to >=22.12.0 or pin a compatible migrations dependency.

   Prompt To Fix With AI

   This is a comment left during a code review.
   Path: package.json
   Line: 89-91
   
   Comment:
   **Align Node engine**
   `@workos/migrations@2.4.0` now resolves `commander@15.0.0`, whose lockfile entry requires `node >=22.12.0` (`pnpm-lock.yaml` lines 1636-1638). This package still advertises `>=22.11`, so users on Node `22.11.x` satisfy the CLI engine but install a dependency tree with an unmet engine requirement; with `engine-strict`, installs reject for a supported runtime. Please raise the root engine to `>=22.12.0` or pin a compatible migrations dependency.
   
   How can I resolve this? If you propose a fix, please make it concise.

2. General comment

   @workos/migrations 2.4.0 does not expose claimed unified export provider commands or nameAttribute help

   • Bug
     • The dependency update on package.json line 55 resolves @workos/migrations 2.4.0, and export-template is now available. However, the claimed migrations CLI surface is only partially delivered: node ./node_modules/@workos/migrations/dist/index.js export --help, export saml --help, export oidc --help, and export authkit --help all print the top-level command list, with no export command or provider-specific help. The aggregate help check also finds no nameAttribute text. This means the PR does not satisfy the stated contract that unified export <provider> and nameAttribute-related help/features are available on head.
   • Cause
     • The package bump to @workos/migrations 2.4.0 brings export-template and split SAML/OIDC template names, but the installed CLI does not register a unified export command with provider subcommands and does not expose nameAttribute in the checked help surface.
   • Fix
     • Update to a @workos/migrations version that actually includes the unified export <provider> command surface and nameAttribute-related CLI/help support, or adjust the dependency contract/PR claims to only promise the features present in 2.4.0.

   _{Ran code and verified through T-Rex}